London Borough of Islington
Brownfield land
There is a problem
- 116 entries must have valid URIs
P120513
- SiteReference
- P120513
- SiteReference
- P120513
- SiteNameAddress
- 141-143, 145 -147 Whitecross Street
- Deliverable
- yes
- HazardousSubstances
- Hectares
- 0.04
- MinNetDwellings
- NetDwellingsRangeFrom
- 7
- NetDwellingsRangeTo
- 7
- OwnershipStatus
- not owned by a public authority
- PermissionDate
- 2013-01-08
- PermissionType
- full planning permission
- PlanningHistory
- http://planning.islington.gov.uk/Northgate/PlanningExplorer/Generic/StdDetails.aspx?PT=Planning%20Applications%20On-Line&TYPE=PL/PlanningPK.xml&PARAM0=318164&XSLT=/Northgate/PlanningExplorer/SiteFiles/Skins/Islington/xslt/PL/PLDetailsSiteHistory.xslt&FT=Planning%20Application%20Details&PUBLIC=Y&XMLSIDE=/Northgate/PlanningExplorer/SiteFiles/Skins/Islington/Menus/PL.xml&DAURI=PLANNING
- PlanningStatus
- permissioned
- SiteplanURL
- http://mapapp.islington.gov.uk/mapthatol/Login.aspx?user=public&utm_content=stcms2.islington.gov.uk
- GeoX
- POINT(-0.093042 51.52292)
- GeoY
- POINT(-0.093042 51.52292)
- Notes
- Site plan is available on Islington interactive mapping website. Specific site is identifiable via SiteReference and SiteNameAddress attribute data.. Demolition of existing buildings/extensions including four residential units. Conversion of the upper floors to create seven residential units; creation of other non housing development.
- OrganisationLabel
- OrganisationURI
- LastUpdatedDate
- 2021-12-14
- FirstAddedDate
- 2017-11-24
- EndDate
- 2021-12-14
How to fix this issue
Your dataset is missing the PlanningHistory column.
The Brownfield land guidance explains how to fix the issue:
PlanningHistory
Enter links to any web pages that give information on the site’s planning history (include the “http://” or “https://” prefix). Fields in this column can contain more than one link, as long as you separate multiple links with the pipe character (‘|’). You can leave this field blank.
How to improve London Borough of Islington’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL